The long story short: I'm trying to schedule a SSIS package that runs a powershell script/command via a proxy account. The problem seems to be that proxy account didn't have the required permissions to run a .ps1 script, so I've changed the execution policy to "Unrestricted" of everything that could be changed:

                                  Scope                         ExecutionPolicy
                                  -----                         ---------------
                          MachinePolicy                            Unrestricted
                             UserPolicy                            Unrestricted
                                Process                               Undefined
                            CurrentUser                            Unrestricted
                           LocalMachine                            Unrestricted

So far, so good! But when I try to execute the SSIS package with a PS command like this:

powershell.exe -file D:\script.ps1 -FileName testme

I got the error:

AuthorizationManager check failed.
    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecord 
   Exception
    + FullyQualifiedErrorId : UnauthorizedAccess

And when I try the more simple command:

powershell.exe -Command &{Get-ExecutionPolicy}

Get-ExecutionPolicy : Access denied At line:1 char:3
+ &{Get-ExecutionPolicy}
+   ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ExecutionPolicy], Managem 
   entException
    + FullyQualifiedErrorId : System.Management.ManagementException,Microsoft. 
   PowerShell.Commands.GetExecutionPolicyCommand

• Edited by Vesko Jl 18 hours 26 minutes ago

The account is a regular user, not an admin. I can connect with it and execute the same powershell script without a problem.

The message is clear "Access Denied" - the account does not have permission.

You need to find what, in your script, is causing access denied.

SSIS processes cannot elevate a user above what is allowed by the SSIS agent account.  Trying to impersonate will not get you around this.

An Access violation is just that and has no relation to an execution policy.

Try to get your script down two or three lines that cause the issue and I will try to show you how to fix it.

As I said. I tried to execute directly a powershell command, avoiding the script security complications. And the following doesn't work:

-Command &{Get-ExecutionPolicy}

-Command &{whoami}

SSIS processes cannot elevate a user above what is allowed by the SSIS agent account.  Trying to impersonate will not get you around this.

An Access violation is just that and has no relation to an execution policy.

Try to get your script down two or three lines that cause the issue and I will try to show you how to fix it.